Technique for time-sensitive networking over a radio access network

ABSTRACT

A technique for Time-Sensitive Networking, TSN, over a radio access network, RAN, is described. As to a handling method aspect of the technique, system information is received from a radio base station of the RAN. The system information is implicative or indicative of support for TSN through the radio base station. Depending on the received system information, at least one TSN stream of the TSN through the radio base station is established or initiated to establish.

CROSS REFERENCE TO RELATED APPLICATIONS

This application is a 35 U.S.C. § 371 national stage application of PCTInternational Application No. PCT/EP2018/073515 filed on Aug. 31, 2018,the disclosure and content of which is incorporated by reference hereinin its entirety.

TECHNICAL FIELD

The present disclosure generally relates to a technique forTime-Sensitive Networking (TSN) over a radio access network (RAN). Morespecifically, methods and devices are provided for handling TSN over aRAN, announcing TSN over a RAN, and distributing a configuration messagefor TSN over a RAN.

BACKGROUND

Factory automation, i.e., automation in a manufacturing plant (orbriefly: factory), requires networking with high reliability and lowlatency. The concept of “Industry 4.0” is an example for factoryautomation. Candidate technologies for such networking includeconventional Time Sensitive Networking (TSN) as standardized by the IEEE802.1 TSN Task Group and the fifth generation (5G) mobile communicationstechnology currently standardized by the Third Generation PartnershipProject (3GPP). For example, the 3GPP document RP-181479 has initiated astudy item for upcoming 3GPP Release 16 to support TSN for factoryautomation.

The conventional TSN technology is based on the IEEE 802.3 Ethernetstandard, which is an example of wired communication. Legacy Ethernet isdesigned for best-effort communication, and the conventional TSNtechnology adds a collection of features to achieve deterministicnetworking over Ethernet. In contrast, 5G mobile communicationstechnology involves wireless radio communication using Long TermEvolution (LTE) and/or New Radio (NR) according to the 3GPP.

At least some units of factory automation, such as autonomous,multifunctional, and/or mobile machinery and robots, require networkingby means of wireless radio communication. However, a factory unit actingas a mobile terminal of the RAN, e.g., a 3GPP user equipment (UE), wouldhave to establish a radio connection with a radio base station of theRAN just to find out that this particular radio base station does notsupport TSN.

SUMMARY

Accordingly, there is a need for a technique that enables TSN overwireless radio communication. An alternative or more specific object isto enable a mobile terminal to specifically select a radio base stationthat supports TSN, preferably prior to establishing a radio connectionbetween the mobile terminal and the radio base station.

As to a first aspect, a method of handling Time-Sensitive Networking(TSN) over a radio access network (RAN) is provided. The methodcomprises a step of receiving system information (SI) from a radio basestation (RBS) of the RAN. The SI is implicative or indicative of supportfor TSN through the RBS. The method further comprises a step ofestablishing or initiating to establish, depending on the received SI,at least one TSN stream of the TSN through the RBS.

In at least some embodiments, energy (e.g., driving a power amplifier orradio transmission), time (e.g., a delay caused by the wireless radiocommunication), and/or radio resources (e.g., transmission timeintervals, subcarriers or spatial streams) can be used more efficientlyin the RAN, e.g., by one or more mobile terminals of the RAN and/or theRBS of the RAN. At least some embodiments can avoid an unnecessaryrandom access (RA) procedure, an unnecessary radio resource control(RRC) connection, and/or an unnecessary initial attach (IA) procedure,or any other procedure to access or connect with the RAN or register toa core network (CN). The IA procedure may comprise a default bearersetup. Same or further embodiments can enable the mobile terminal toestablish a TSN stream quicker or with less delay. The RAN and the CNare collectively referred to as the network.

By means of the SI, embodiments of the technique can enable the mobileterminal to determine if TSN and/or which TSN features are supported bythe network (e.g., through the RBS) before being attached to network.Optionally, TSN information may be broadcasted by the RBS, e.g., in theSI. Preferably, the mobile terminal (e.g., only) conditionallyestablishes a connection to the RAN (e.g., to the RBS), if the SI (e.g.,the TSN information) indicates that the RAN (e.g., that the RBS)fulfills TSN requirements of the mobile terminal (e.g., TSN requirementsof a TSN application of the mobile terminal or TSN requirements of a TSNapplication using the mobile terminal for TSN).

The received SI may imply that TSN is not supported through the RBS. Forexample, receiving SI that is silent on TSN (e.g., silent on any TSNfeature and/or any TSN configuration) may imply that the TSN is notsupported through the RBS. If the received SI indicates (i.e., isindicative) or implies (i.e., is implicative) that the RBS does notsupport TSN, a mobile terminal may refrain from initiating to establisha TSN stream through the RBS (i.e., no TSN stream is established usingthe particular RBS) based on the received SI.

If the SI received from two or more RBSs indicates (i.e., is indicative)or implies (i.e., is implicative) that the respective RBS supports TSN,the mobile terminal may select one of the two or more RBSs based on thereceived SIs.

The method may be performed by a user equipment (UE). Herein, theexpression “UE” may encompass any mobile terminal configured forperforming a random access procedure with the RBS or any other RBS ofthe RAN and/or configured for establishing a radio connection with theRBS or any other RBS of the RAN.

The UE may be a 3GPP UE, a mobile or portable station (STA, e.g. a Wi-FiSTA), a device for machine-type communication (MTC), a device for theInternet of Things (IoT) or a combination thereof. Examples for the UEinclude robots, sensors and/or actuators, e.g., in manufacturing,automotive communication and home automation. The MTC device or the IoTdevice may be implemented in household appliances and consumerelectronics. Examples for the combination include a self-drivingvehicle.

Furthermore, the UE may be a talker and/or a listener of the TSN and/orthe at least one TSN stream.

As to a second aspect, a method of announcing Time-Sensitive Networking(TSN) over a radio access network (RAN) is provided. The methodcomprises a step of transmitting system information (SI) from a radiobase station (RBS) of the RAN. The SI is implicative or indicative ofsupport for TSN through the RBS. The method further comprises a step ofsupporting, according to the transmitted SI, at least one TSN stream ofthe TSN through the RBS.

The RBS may perform the method. The SI may be transmitted to a UE, Theat least one TSN stream may be terminated at the UE.

The technique may be implemented at the RAN. The RBS may serve a cell ofthe RAN. The RBS may encompass any station that is configured to provideradio access to the UE. The RBS may serve a plurality of UEs. The secondaspect of the technique may be implemented once at the RBS with respectto each of the served UEs. The first aspect of the technique may beimplemented at each of the served UEs.

The second method aspect may cooperate with and/or trigger the firstmethod aspect.

As to a third aspect, a method of distributing a configuration messagefor Time-Sensitive Networking (TSN) over a radio access network (RAN) isprovided. The method comprises a step of determining at least oneconfiguration message indicative of support for the TSN through at leastone radio base station (RBS) of the RAN. The method further comprises astep of sending the configuration message from a core network (CN) toeach of the at least one RBS of the RAN.

The configuration message may trigger each RBS that receives theconfiguration message to send the SI and/or support the at least one TSNstream. For example, reception of the configuration message indicativeof support for the TSN may trigger sending SI that is indicative orimplicative of support for the TSN. The CN may be connected to the RAN.

The method may be performed by the CN, e.g., by an Access and MobilityManagement Function or, briefly, Access Management Function (AMF).Alternatively or in addition, the method may be performed by a TSNnetwork, e.g., a centralized user configuration (CUC) or a centralizednetwork configuration (CNC).

The third method aspect may cooperate with and/or trigger the secondmethod aspect.

In any aspect, the RBS may be a distributed base station or a componentof a cloud-RAN (C-RAN). The RBS may be implemented by at least one of abaseband unit (BBU) and one or more radio function units (RFU, e.g.,remote radio heads or RRH) connected to the BBU. The at least one TSNstream may be established through the RFU from which the SI has beenreceived or through another RFU of the RAN.

Examples for the RBS may include a 2G base station or Base TransceiverStation (BTS), a 3G base station or Node B (NB), 4G base station oreNodeB (eNB), a 5G base station or gNodeB (gNB), and an access point(e.g., a Wi-Fi access point or AP). The RAN may be implemented accordingto the Global System for Mobile Communications (GSM), the UniversalMobile Telecommunications System (UMTS), Long Term Evolution (LTE), NewRadio (NR), and/or IEEE 802.11 or Wi-Fi. The CN may a 5G core networkaccording to 3GPP.

The technique may be implemented on a Physical Layer (PHY), a MediumAccess Control (MAC) layer, a Radio Link Control (RLC) layer, a RadioResource Control (RRC) layer of a protocol stack for the radiocommunication, an S1 application protocol (S1-AP), a reference point NG2and/or a non-access stratum (NAS).

The TSN may be based on or may comprise any feature for ultra-reliableand/or low-latency communications (URLLC), e.g., transmission timeinterval (TTI) structures for low latency and/or methods for improvedreliability defined for 3GPP NR in Release 15 or 16.

The technique may implement TSN for radio transmissions and/or a radionetwork, e.g., for a 5G cellular RAN or NR access network. Herein,networking may encompass bilateral or multilateral communication betweennodes of a network, e.g., the UEs. Use cases of the technique mayinclude factory automation, i.e., the technique may implement factoryautomation networking. Use cases may include (e.g., pure) plantmeasurements, e.g., for precise motion control in a robotized factorycell.

The technique may enable a wireless networking that fulfills therequirements of networking for factory automation, e.g. manufacturingaccording to the concept of “Industry 4.0”. Herein, factory automation,particularly the concept of “Industry 4.0”, may comprise at least one ofcyber-physical systems, the Internet of Things (IoT), cloud computingand cognitive computing.

As to another aspect, a computer program product is provided. Thecomputer program product comprises program code portions for performingany of the steps of the first method aspect, the second method aspectand/or the third method aspect disclosed herein when the computerprogram product is executed by one or more computing devices. Thecomputer program product may be stored on a computer-readable recordingmedium. The computer program product may also be provided for downloadvia a data network, e.g., over the RAN, via the Internet, and/or throughthe RBS. Alternatively or in addition, the method may be encoded in aField-Programmable Gate Array (FPGA) and/or an Application-SpecificIntegrated Circuit (ASIC), or the functionality may be provided fordownload by means of a hardware description language.

As to a first device aspect, a device for handling Time-SensitiveNetworking (TSN) over a radio access network (RAN) is provided. Thedevice is configured to perform the first method aspect. Alternativelyor in addition, the device comprises a receiving unit configured toreceive system information (SI) from a radio base station (RBS) of theRAN. The SI is implicative or indicative of support for TSN through theRBS. The device further comprises an establishing unit configured toestablish or initiate to establish, depending on the received SI, atleast one TSN stream of the TSN through the RBS.

As to a further first device aspect, a device for handlingTime-Sensitive Networking (TSN) over a radio access network (RAN) isprovided. The device comprises at least one processor and a memory. Saidmemory comprises instructions executable by said at least one processorwhereby the device is operative to perform the first method aspect.Alternatively or in addition, execution of the instructions causes thedevice to be operative to receive system information (SI) from a radiobase station (RBS) of the RAN. The SI is implicative or indicative ofsupport for TSN through the RBS. Execution of the instructions furthercauses the device to be operative to establish or initiate establishing,depending on the received system information, at least one TSN stream ofthe TSN through the RBS.

As to a still further first device aspect, a device for handlingTime-Sensitive Networking (TSN) over a radio access network (RAN) isprovided. The device comprises one or more modules for performing thefirst method aspect. Alternatively or in addition, the device comprisesa system information (SI) reception module for receiving SI from a radiobase station (RBS) of the RAN. The SI is implicative or indicative ofsupport for TSN through the RBS. The device further comprises a TSNstream module for establishing or initiating to establish, depending onthe received system information, at least one TSN stream of the TSNthrough the RBS.

As to a second device aspect, a device for announcing Time-SensitiveNetworking (TSN) over a radio access network (RAN) is provided. Thedevice is configured to perform the second method aspect. Alternativelyor in addition, the device comprises a transmitting unit configured totransmit system information (SI) from a radio base station (RBS) of theRAN. The SI is implicative or indicative of support for TSN through theRBS. The device further comprises a supporting unit configured tosupport, according to the transmitted SI, at least one TSN stream of theTSN through the RBS.

As to a further second device aspect, a device for announcingTime-Sensitive Networking (TSN) over a radio access network (RAN) isprovided. The device comprises at least one processor and a memory. Saidmemory comprises instructions executable by said at least one processorwhereby the device is operative to perform the second method aspect.Alternatively or in addition, execution of the instructions causes thedevice to be operative to transmit system information (SI) from a radiobase station (RBS) of the RAN. The SI is implicative or indicative ofsupport for TSN through the RBS. Execution of the instructions furthercauses the device to be operative to support, according to thetransmitted SI, at least one TSN stream of the TSN through the RBS.

As to a still further second device aspect, a device for announcingTime-Sensitive Networking (TSN) over a radio access network (RAN) isprovided. The device comprises one or more modules for performing thesecond method aspect. Alternatively or in addition, the device comprisesa system information (SI) transmission module for transmitting SI from aradio base station (RBS) of the RAN, wherein the SI is implicative orindicative of support for TSN through the RBS. The device furthercomprises a TSN stream module for supporting, according to thetransmitted SI, at least one TSN stream of the TSN through the RBS.

As to a third device aspect, a device for distributing a configurationmessage for Time-Sensitive Networking (TSN) over a radio access network(RAN) is provided. The device is configured to perform the third methodaspect. Alternatively or in addition, the device comprises a determiningunit configured to determine at least one configuration messageindicative of support for the TSN through at least one radio basestation of the RAN. The device further comprises a sending unitconfigured to send the configuration message from a core network (CN) toeach of the at least one RBS of the RAN.

As to a further third device aspect, a device for distributing aconfiguration message for Time-Sensitive Networking (TSN) over a radioaccess network (RAN) is provided. The device comprises at least oneprocessor and a memory. Said memory comprises instructions executable bysaid at least one processor whereby the device is operative to performthe third method aspect. Alternatively or in addition, execution of theinstructions causes the device to be operative to determine at least oneconfiguration message indicative of support for the TSN through at leastone radio base station (RBS) of the RAN. Execution of the instructionsfurther causes the device to be operative to send the configurationmessage from a core network (CN) to each of the at least one RBS of theRAN.

As to a still further third device aspect, a device for distributing aconfiguration message for Time-Sensitive Networking (TSN) over a radioaccess network (RAN) is provided. The device comprises one or moremodules for performing the third method aspect. Alternatively or inaddition, the device comprises a configuration determining module fordetermining at least one configuration message indicative of support forthe TSN through at least one radio base station (RBS) of the RAN. Thedevice further comprises a configuration sending module for sending theconfiguration message from a core network (CN) to each of the at leastone RBS of the RAN.

As to a still further aspect, a user equipment (UE) configured tocommunicate with a radio base station (RBS) is provided. The UEcomprises a radio interface and processing circuitry configured toexecute any of the steps of the first method aspect.

As to a still further aspect, a radio base station (RBS) configured tocommunicate with a user equipment (UE) is provided. The RBS comprises aradio interface and processing circuitry configured to execute any ofthe steps of the second method aspect.

As to a still further aspect, an Access Management Function (AMF)configured to communicate with a user equipment (UE) and/or a radio basestation (RBS) is provided. The AMF comprises an interface (e.g., aninterface S1 and/or a next generation reference point NG2) andprocessing circuitry configured to execute any of the steps of the thirdmethod aspect.

As to a still further aspect, a communication system including a hostcomputer is provided. The host computer may comprise a processingcircuitry configured to provide user data. The host computer may furthercomprise a communication interface configured to forward user data to aCN and/or a RAN (e.g., a cellular network) for transmission to a userequipment (UE). The UE may comprise a radio interface and processingcircuitry, the processing circuitry of the UE being configured toexecute any of the steps of the first method aspect. Alternatively or inaddition, the RAN may comprise a RBS comprising a radio interface andprocessing circuitry, the processing circuitry of the RBS beingconfigured to execute any of the steps of the second method aspect.Alternatively or in addition, the CN may comprise an AMF comprising aninterface and processing circuitry, the processing circuitry of the AMFbeing configured to execute any of the steps of the third method aspect.

The communication system may further comprise the UE. Alternatively orin addition, the communication system may further comprise the RBSconfigured to communicate with the UE. Alternatively or in addition, thecommunication system may further comprise the AMF configured tocommunicate with the RBS.

The processing circuitry of the host computer may be configured toexecute a host application, thereby providing the user data.Alternatively or in addition, the processing circuitry of the UE may beconfigured to execute a client application associated with the hostapplication.

As to a still further aspect, a method implemented in a UE is provided.The method may comprise any of the steps of the first method aspect.

As to a still further aspect, a method implemented in a RBS is provided.The method may comprise any of the steps of the second method aspect.

As to a still further aspect, a method implemented in an AMF isprovided. The method may comprise any of the steps of the third methodaspect.

Any of the devices (e.g., any UE, RBS, AMF and/or host computer forembodying the technique) or the communication system may further includeany feature disclosed in the context of any of the method aspects, andvice versa. Particularly, any one of the devices, units, and modules, ora dedicated unit or module of the respective device, may be configuredto perform or trigger one or more of the steps of any one of the methodaspects.

BRIEF DESCRIPTION OF THE DRAWINGS

Further details of embodiments of the technique are described withreference to the enclosed drawings, wherein:

FIG. 1 shows a schematic block diagram for an embodiment of a device forhandling Time-Sensitive Networking over a radio access network;

FIG. 2 shows a schematic block diagram for an embodiment of a device forannouncing Time-Sensitive Networking over a radio access network;

FIG. 3 shows a schematic block diagram for an embodiment of a device fordistributing a configuration message for Time-Sensitive Networking overa RAN;

FIG. 4 shows a flowchart for implementing a method of handlingTime-Sensitive Networking over a radio access network, which isimplementable by the device of FIG. 1;

FIG. 5 shows a flowchart for implementing a method of announcingTime-Sensitive Networking over a radio access network, which isimplementable by the device of FIG. 2;

FIG. 6 shows a flowchart for implementing a method of distributing aconfiguration message for Time-Sensitive Networking over a radio accessnetwork, which is implementable by the device of FIG. 3;

FIG. 7 shows a schematic block diagram of a first example of acommunication system comprising embodiments of the devices of FIGS. 1 to3;

FIG. 8 shows a schematic block diagram of a second example of acommunication system comprising embodiments of the devices of FIGS. 1 to3;

FIG. 9 shows a schematic block diagram of a third example of acommunication system comprising embodiments of the devices of FIGS. 1 to3;

FIG. 10 shows a functional block diagram of a fourth example of acommunication system comprising embodiments of the devices of FIGS. 1 to3;

FIG. 11 shows a first schematic signaling diagram for a communicationsystem comprising embodiments of the devices of FIGS. 1 to 3;

FIG. 12 shows a second schematic signaling diagram for a communicationsystem comprising embodiments of the devices of FIGS. 1 to 3;

FIG. 13 shows a schematic block diagram of an embodiment of the deviceof FIG. 1;

FIG. 14 shows a schematic block diagram of an embodiment of the deviceof FIG. 2;

FIG. 15 shows a schematic block diagram of an embodiment of the deviceof FIG. 3;

FIG. 16 schematically illustrates a telecommunication network connectedvia an intermediate network to a host computer;

FIG. 17 shows a generalized block diagram of a host computercommunicating via a radio base station with a user equipment over apartially wireless connection; and

FIGS. 18 and 19 show flowcharts for methods implemented in acommunication system including a host computer, a radio base station anda user equipment.

DETAILED DESCRIPTION

In the following description, for purposes of explanation and notlimitation, specific details are set forth, such as a specific networkenvironment in order to provide a thorough understanding of thetechnique disclosed herein. It will be apparent to one skilled in theart that the technique may be practiced in other embodiments that departfrom these specific details. Moreover, while the following embodimentsare primarily described for a 5G New Radio (NR) implementation, it isreadily apparent that the technique described herein may also beimplemented in any other radio network, including 3GPP LTE or asuccessor thereof and Wireless Local Area Network (WLAN or Wi-Fi)according to the standard family IEEE 802.11.

Moreover, those skilled in the art will appreciate that the functions,steps, units and modules explained herein may be implemented usingsoftware functioning in conjunction with a programmed microprocessor, anApplication Specific Integrated Circuit (ASIC), a Field ProgrammableGate Array (FPGA), a Digital Signal Processor (DSP) or a general purposecomputer, e.g., including an Advanced RISC Machine (ARM). It will alsobe appreciated that, while the following embodiments are primarilydescribed in context with methods and devices, the invention may also beembodied in a computer program product as well as in a system comprisingat least one computer processor and memory coupled to the at least oneprocessor, wherein the memory is encoded with one or more programs thatmay perform the functions and steps or implement the units and modulesdisclosed herein.

FIG. 1 schematically illustrates a block diagram for an embodiment of adevice for handling Time-Sensitive Networking (TSN) over a radio accessnetwork (RAN). The device is generically referred to by reference sign100.

The device 100 comprises a system information reception module 102 thatreceives system information (SI) from a radio base station (RBS) of theRAN. The SI is implicative or indicative of support (e.g., implicativeor indicative as to the support) for TSN through the RBS, For example,the SI implies or indicates whether or not TSN is supported through theRBS. The device 100 further comprises a TSN stream module 104 thatestablishes or initiates establish, depending on the received SI, atleast one TSN stream of the TSN through the RBS.

FIG. 2 schematically illustrates a block diagram for an embodiment of adevice for announcing TSN over a RAN. The device is generically referredto by reference sign 200.

The device 200 comprises a system information transmission module 202that transmits (e.g., broadcasts) SI from a RBS of the RAN. The SI isimplicative or indicative of support (e.g., implicative or indicative asto the support) for TSN through the RBS. The device 200 furthercomprises a TSN stream module 204 that supports, according to thetransmitted SI, at least one TSN stream of the TSN through the RBS.

The device 200 may be connected to and/or part of the RAN. The device200 may be embodied by or at the RBS of the RAN, nodes connected to theRBS or the RAN for controlling the RBS or a combination thereof.

The SI may be transmitted to an UE embodying the device 100. RBS fromwhich the SI is received at the device 100 may be embodied by the device200. The RAN referred to in the context of the device 100 may be the RANreferred to in the context of the device 200.

FIG. 3 schematically illustrates a block diagram for an embodiment of adevice for distributing a configuration message for TSN over a RAN. Thedevice is generically referred to by reference sign 300.

The device 300 comprises a configuration determining module 302 thatdetermines at least one configuration message that is implicative orindicative of support (e.g., implicative or indicative as to thesupport) for the TSN through at least one RBS of the RAN. The device 300further comprises a configuration sending module 304 that sends the atleast one configuration message from a core network (CN) to each of theat least one RBS of the RAN.

The device 300 may be connected to and/or part of a CN serving the RANand/or the at least one RBS. The device 300 may be embodied by or at anAccess Management Function (AMF) or a Mobility Management Entity (MME)of the CN, nodes connected to the AMF, MME, or the CN for controllingthe RBS, or a combination thereof.

Each of the at least one RBS may be an embodiment of the device 200.Each of the at least one RBS 200 may transmit its SI based on theconfiguration message received from the device 300.

Any of the modules of any of the devices 100, 200, and 300 may beimplemented by units configured to provide the correspondingfunctionality.

In the context of any one of the device aspects, the device 100 may be auser equipment (UE, i.e., a mobile terminal or radio device) configuredfor a radio connection with the RBS. The UE 100 may be embodied by a TSNapplication, the UE 100 may comprise the TSN application, or the UE 100may act as a networking interface for the TSN application. The TSNapplication may be a manufacturing robot or a self-driving vehicle.

The RBS embodying the device 200 may encompass a network controller(e.g., a Wi-Fi access point) or a radio access node (e.g. a 3G Node B, a4G eNodeB, or a 5G gNodeB) of the RAN. The RBS 200 may be configured toprovide radio access to the UE 100.

FIG. 4 shows a flowchart for a method 400 of handling TSN over a RAN.The method 400 comprises a step 402 of receiving SI from a RBS of theRAN. The SI is implicative or indicative as to support for TSN throughthe RBS. The SI may be RBS-specific. The method 400 further comprises astep 404 of establishing or initiating to establish, depending on thereceived SI, at least one TSN stream of the TSN through the RBS.

The method 400 may be performed by the device 100, e.g., the UE 100radio-connected or radio-connectable to the RAN. For example, themodules 102 and 104 may perform the steps 402 and 404, respectively.

FIG. 5 shows a flowchart for a method 500 of announcing TSN over a RAN.The method 500 comprises a step 502 of transmitting SI from a RBS of theRAN. The SI is implicative or indicative as to support for TSN throughthe RBS. The SI may be RBS-specific. The method 500 further comprises astep 504 of supporting, according to the transmitted SI, at least oneTSN stream of the TSN through the RBS.

The method 500 may be performed by the device 200, e.g., at or using theRBS of the RAN. For example, the modules 202 and 204 may perform thesteps 502 and 504, respectively.

FIG. 6 shows a flowchart for a method 600 of distributing aconfiguration message for TSN over a RAN. The method 600 comprises astep 602 of determining at least one configuration message indicative orimplicative as to support for the TSN through at least one RBS of theRAN. The method 600 further comprises a step 604 of sending the at leastone configuration message from a CN to each of the at least one RBS ofthe RAN.

The method 600 may be performed by the CN and/or the device 300, e.g.,at or using a network component of the CN, the AMF or MME, and/or usinga TSN function. The TSN function may be a Centralized NetworkConfiguration (CNC) or a Centralized User Configuration (CUC). Forexample, the modules 302 and 304 may perform the steps 602 and 604,respectively.

The step 404 of establishing or initiating to establish, depending onthe received SI, the at least one TSN stream may comprise selectively(e.g., conditionally) establishing or selectively (e.g., conditionally)initiating to establish the at least one TSN stream. The selectivity(e.g., conditionality) may be dependent on the received SI. The UE maydecide, based on the SI from the RBS, whether to attempt establishingthe TSN stream, e.g., prior to accessing or connecting with the basestation, or not.

The step 404 of establishing or initiating to establish the at least oneTSN stream may comprise selectively performing or selectively initiatingto perform at least one of a random access procedure with the RBS 200 ofthe RAN; a radio resource control (RRC) connection setup with the RBS(200) of the RAN; and a network attach procedure with a CN connected tothe RAN. The selectivity may be dependent on the received SI.

The establishing step 404 may comprise performing or initiating toperform a TSN application that uses the at least one established TSNstream. The TSN application or a client of the TSN application may beperformed at the UE 100. The selectivity (e.g., the conditionality) inthe step 404 may be fulfilled if the received SI is indicative of TSNfeatures required by the TSN application.

The step 402 of receiving the SI is performed with respect to each of aplurality of RBSs 200 of the RAN. The step 404 of establishing orinitiating to establish the at least one TSN stream may compriseselecting, among the plurality of RBSs 200, the RBS 200 the SI of whichis indicative of TSN features required by the TSN application.

The RBS which best fulfills the required TSN features according to therespective SI may be selected (e.g., if none of the plurality of RBSsfulfills the required TSN features). Alternatively or in addition, theRBS which SI is indicative of the most preferably TSN features may beselected (e.g., if more than one of the plurality of RBSs fulfills therequired TSN features).

The method 400 may further comprise a step of sending a control messageto the CN. The control message may be indicative of TSN featuresrequired by the TSN application. The control message may be a non-accessstratum (NAS) message.

The control message may be indicative of a request for the TSN. Thecontrol message may be forwarded to the CUC.

The SI may be implicative or indicative of at least one TSN featuresupported by or through the RBS 200. The SI may be RBS-specific. Theselectivity (e.g., the conditionality) in the step 404 may be dependenton the at least one supported TSN feature. Alternatively or in addition,the TSN stream may be established over the RAN depending on the at leastone supported TSN feature. For example, the establishing of the at leastone TSN stream may comprise performing or initiating to perform therandom access with the RBS depending on the at least one supported TSNfeature.

Herein, the TSN feature may encompass any feature or functionalityavailable at the RBS for the TSN. The at least one TSN feature supportedthrough the RBS may also be referred to as TSN capability of the RBS.

The at least one TSN feature may comprise at least one of atime-synchronization, a latency bound for the at least one TSN stream,and a reliability measure for the at least one TSN stream. Thetime-synchronization may be a time-synchronization of RBSs 200 and/ornetwork components processing (e.g., transporting) the at least one TSNstream.

Alternatively or in addition, the SI may be indicative of a TSNconfiguration (also, TSN configuration scheme) for the TSN through theRBS 200. For example, the establishing 404 of the at least one TSNstream may comprise performing or initiating a TSN setup according tothe TSN configuration. The TSN configuration may be indicative of anavailability or unavailability of at least one of a CNC and a CUC.

The SI may be broadcasted from the RBS 200 in the step 502. The SI maybe a broadcast message. The SI may be comprised in one or more systeminformation blocks (SIBs).

The method 500 may further comprise a step of receiving a configurationmessage indicative of the support for TSN from the CN at the RBS 200.The SI transmitted by the RBS 200 may be derived from the receivedconfiguration message.

The SI may be implicative or indicative of at least one TSN featuresupported by or through the RBS 200. The SI may be broadcasted in one ormore SIBs.

The method 500 may further comprise any feature and/or step disclosed inthe context of the device 100 and the method 400, or any feature or stepcorresponding thereto.

The configuration message may be sent from the AMF of the CN.

The configuration message may be implicative or indicative of at leastone TSN feature supported or supposed to be supported by or through theRBS 200.

The method 600 may further comprise any feature or step of the methods400 and 500, or any feature or step corresponding thereto.

Embodiments of the technique maintain compatibility with the 3GPPdocument TS 23.501, version 15.1.0, specifying “System Architecture forthe 5G System” (Stage 2), or a successor thereof.

A network (e.g., a 5G network comprising the RAN providing NR access asdefined by 3GPP) is configured to support TSN transmissions through atleast some RBSs. For a UE to become attached to such a TSN network overthe RAN (e.g., 5G radio or NR), there is no existing way to getinformation as to whether the network in general, and the RBS (e.g., agNB) specifically, supports TSN transmissions or not. In embodiments ofthe technique, the SI enables the UE 100 to determine if and/or howcertain TSN features are supported, before getting into radio resourcecontrol (RRC) connected mode and further signaling with the 5G network.Thus, the technique enables the UE 100 and, therefore, also a TSNapplication the UE 100 is connected to, to be aware of whether, whichand/or how TSN features are supported by the network, specifically theRAN and/or the RBS transmitting the SI.

The SI may be implicative or indicative as to the support of TSNfeatures. The TSN features may comprise at least one of timesynchronization, redundancy, reliability, and latency (e.g., anestimated end-to-end latency).

Embodiments of the technique enable the UE 100 to receive necessaryTSN-related information in the SI before getting attached to the 5Gnetwork. In this way, the UE 100 is aware of which TSN features aresupported by the 5G network.

Furthermore, the 5G network may inform one or more UEs 100 in the sameway about configuration details of the TSN network and/or how to, forexample, perform time synchronization and network management.

For example, not all RBSs (e.g., gNBs) covering an area (e.g., deployedin a factory hall) support TSN traffic. The technique may be implementedto block those UEs 100 (also: TSN-UEs) that require TSN traffic fromcertain RBSs (e.g., gNBs), e.g., from those RBSs that do not support TSNor not the TSN features required by the UE 100.

The SI may be implemented by one or more System Information Blocks(SIBs).

An overall functionality and structure of a Master Information Block(MIB) and SIBs for NR may be essentially the same as for LTE. Adifference between NR and LTE is that in NR provides two different typesof SIBs. A first type of SIBs is transmitted periodically, e.g., equalor similar to SIB transmissions in LTE. A second type of SIBs istransmitted only when there is the request from the UE 100.

The SIBs are broadcasted by the RBS 200 (e.g., a gNB) and include themain part of the system information the UE 100 requires to access a cellserved by the RBS 200 and other information on cell reselection. SIBsare transmitted over a Downlink Shared Channel (DL-SCH). The presence ofthe system information on the DL-SCH in a subframe is indicated by thetransmission of a corresponding Physical Downlink Control Channel(PDCCH) marked with a special system-information Radio Network TemporaryIdentifier (SI-RNTI).

A number of the different SIBs are defined by 3GPP for LTE and NR, e.g.,characterized by the type of the information included in the SIBs. Thissystem information informs the UE 100 about the network capabilities.Not all SIBs are supposed to be present. SIBs are broadcasted repeatedlyby the RBS 200 (e.g., the gNB).

Within a TSN network, i.e., a network supporting TSN, the communicationendpoints are called TSN talker and TSN listener. At least one of theTSN talker and the TSN listener is an UE embodying the device 100. Forthe support of TSN, all RBSs 200 and network components (e.g., switches,bridges, or routers, which optionally embody the device 300) between theTSN talker and the TSN listener support certain TSN features, e.g. IEEE802.1AS time synchronization. All nodes (e.g., RBSs and/or networkcomponents) that are synchronized in the network belong to a so-calledTSN domain. TSN communication is only possible within such a TSN domain.

The device 300 may be embodied by one or more nodes or networkcomponents in the CN or the TSN network. Herein, in the description ofembodiments, such alternative locations are referred to by referencesigns of the form 300-x for the x-th location.

TSN for a RAN or a RAN configured for TSN may comprise features fordeterministic networking, which are also referred to as TSN features.The TSN features may comprise at least one of time synchronization,guaranteed (e.g., low) latency transmissions (e.g., an upper bound onlatency), and guaranteed (e.g., high) reliability (e.g., an upper boundon packet error rate). The time synchronization may comprise a timesynchronization between components of the RAN (e.g., the RBSs 200)and/or network components (e.g., in a backhaul domain and/or the CN).

Optionally, the SI is indicative of the TSN features supported throughthe respective RBS 200.

The supported TSN features may comprise or be compatible with at leastone of the following group of categories. A first category comprisestime synchronization, e.g. according to the standard IEEE 802.1AS. Asecond category comprises bounded low latency, e.g. according to atleast one of the standards IEEE 802.1Qav, IEEE 802.1Qbu, IEEE 802.1Qbv,IEEE 802.1Qch, and IEEE 802.1Qcr. A third category comprisesultra-reliability, e.g. according to at least one of the standards IEEE802.1CB, IEEE 802.1Qca, and IEEE 802.1Qci. A fourth category comprisesnetwork configuration and management, e.g. according to at least one ofthe standards IEEE 802.1Qat, IEEE 802.1Qcc, IEEE 802.1Qcp and IEEE802.1CS.

The configuration and/or management of a TSN network including the RANcan be implemented in different manners, e.g., in a centralized or in adistributed setup as defined by the standard IEEE 802.1Qcc. Examples ofdifferent configuration models are described with reference to FIGS. 7,8 and 9.

FIG. 7 schematically illustrates a block diagram for a first example ofa communications system 700 comprising embodiments of the devices 100,200 and 300. The communication system 700 comprises the RAN 710 and theCN 730. The RAN 710 may comprise at least one embodiment of the device200. The CN 730 may comprise at least one embodiment of the device 300,e.g., a network component 300-1. The network component 300-1 may be aswitch, a bridge or a router. A backhaul domain 720 provides data linksbetween the RBSs 200 of the RAN 710 and/or between the at least one RBS200 and the CN 730. The data links may comprise at least one ofmicrowave links, Ethernet links and fiber optical links.

The SI 712 is broadcasted by the RBS 200 to the UE 100 according to thesteps 402 and 502. The RBS 200 is configured to broadcast the SI 712according to the step 502 and to support the TSN stream according to thestep 504 responsive to the configuration message 722-1 received from orthrough the network component 300-1.

In a scheme for distributed TSN configuration, which is illustrated bythe first example in FIG. 7, there is no CUC and no CNC for the TSNnetwork. The TSN talker 100 is, therefore, responsible for initiation ofa TSN stream in the step 404. As no CNC is present, the networkcomponents 300-1 (e.g., switches or bridges) are configuring themselves,which may not allow using, for example, time-gated queuing as defined inIEEE 802.1Qbv. The distributed TSN configuration may be compatible orconsistent with the document IEEE P802.1Qcc/D2.3, “Draft Standard forLocal and metropolitan area networks—Bridges and Bridged NetworksAmendment: Stream Reservation Protocol (SRP) Enhancements andPerformance Improvements”, IEEE TSN Task Group, e.g., draft status Mar.5, 2018.

In a first scheme for centralized TSN configuration, which isschematically depicted in FIG. 8 for a second example of thecommunication system 700, the TSN talker 100 is responsible forinitialization of the TSN stream in the step 404, while the networkcomponents 300-1 are configured by a CNC 300-2. The centralized TSNconfiguration may be compatible or consistent with the document IEEEP802.1Qcc/D2.3.

The SI 712 is broadcasted by the RBS 200 to the UE 100 according to thesteps 402 and 502. Alternatively or additionally to the configurationmessage 722-1, the RBS 200 is configured to broadcast the SI 712according to the step 502 and to support the TSN stream according to thestep 504 responsive to the configuration message 722-2 received from orthrough the CNC 300-2.

In a second scheme for centralized TSN configuration (also: fullycentralized TSN configuration), which is schematically depicted in FIG.9 for a third example of the communication system 700, the networkcomponents 300-1 are configured by the CNC 300-2 and the CUC 300-3 withnetwork configuration information and user configuration information,respectively. In one implementation, the CUC 300-3 may configure thenetwork components to establish the TSN stream as soon as the TSN talker100 is radio-connected to the RBS 200. In another implementation that iscombinable with the one implementation, the TSN talker 100 isresponsible for initialization of the at least one TSN stream, whilequality requirements of the TSN talker 100 for the at least one TSNstream and/or the number of TSN streams for the TSN talker 100 isconfigured by the CUC 300-3. The fully centralized TSN configuration maybe compatible or consistent with the document IEEE P802.1Qcc/D2.3.

The SI 712 is broadcasted by the RBS 200 to the UE 100 according to thesteps 402 and 502. Alternatively or additionally to the configurationmessage 722-1 and/or the configuration message 722-2, the RBS 200 isconfigured to broadcast the SI 712 according to the step 502 and tosupport the TSN stream according to the step 504 responsive to theconfiguration message 722-3 received from the CUC 300-3.

Optionally, e.g. in any of the three examples for the communicationsystem 700, the SI 712 is transmitted on a broadcast channel of the RAN710. The SI 712 may (e.g., positively) indicate the support of the TSN,e.g., without user and/or network configuration information. The UE 100may receive the user and/or network configuration information on adownlink control channel from the RBS 200, by TSN-specific protocolsand/or from the CN 710 (e.g., the device 300-1) using a non-accessstratum (NAS) protocol. Alternatively or in combination, the SI 712 maycomprise (at least partly) the user and/or network configurationinformation.

The TSN communication between TSN talker (as an embodiment of the device100) and TSN listener (which may or may not be a further embodiment ofthe device 100) happens in TSN streams. A TSN stream is based on certainrequirements in terms of data rate and latency given by an application(TSN application) implemented at the TSN talker and the TSN listener.The TSN configuration and management features are used to setup the TSNstream and to guarantee the requirements of the TSN stream across thenetwork.

In the distributed scheme (e.g., according to the first example in FIG.7), the TSN talker 100 and the TSN listener 100 may use the StreamReservation Protocol (SRP) to setup and configure the at least one TSNstream in every RBS 200 and/or every network component 300-1 (e.g.,every switch) along the path from the TSN talker 100 to the TSN listener100 in the TSN network. Optionally, some TSN features require the CNC300-2 as a central management entity (e.g., according to the secondexample in FIG. 8). The CNC 300-2 uses for example a NetworkConfiguration Protocol (Netconf) and/or “Yet Another Next Generation”(YANG) models to configure the RBS 200 and/or the network components300-1 (e.g., switches) in the network for each TSN stream. This alsoallows the use of time-gated queuing as defined in IEEE 802.1Qbv thatenables data transport in a TSN network with deterministic latency. Withtime-gated queuing on each RBS 200 and/or each network component 300-1(e.g., switch), queues are opened or closed following a precise schedulethat allows high priority packets to pass through the RBS 200 or networkcomponent 300-1 with minimum latency and jitter if it arrives at ingressport within the time the gate is scheduled to be open. In the fullycentralized scheme (e.g., according to the third example in FIG. 9), thecommunication system 700 comprises a CUC 300-3 as a point of contact forthe TSN listener 100 and/or the TSN talker 100. The CUC 300-3 collectsstream requirements and/or endpoint capabilities from the TSN listener100 and/or the TSN talker 100. The CUC 300-3 may communicate with theCNC 300-2 directly. The TSN configuration may be implemented asexplained in the standard IEEE 802.1Qcc in detail.

FIG. 10 shows a functional block diagram for a fourth example of acommunication system 700 comprising embodiments of the devices 100, 200and 300. The fourth example may further comprise any of the featuredescribed for the first, second and/or third example, wherein likereference signs refer to interchangeable or equivalent features. Anoptional interworking between the 5G network (e.g., comprising the RAN710 and the CN 730) and the TSN network architecture (e.g., the CNC300-2 and the CUC 300-3) may be based on at least one of the controlmessages 722-2 and 722-3 from the CNC 300-2 and the CUC 300-3,respectively, e.g., as illustrated in FIG. 10. At least one of thecontrol messages 722-2 and 722-3 may be forwarded to the AMF 300-4 (inthe CN 730) and/or to the RBS 200 (in the RAN 710) using a control planeof the 5G network. Alternatively or in addition, the CN 730, e.g., theAMF 300-4, may implement at least one of the CNC 300-2 and the CUC300-3.

The technique enables connecting TSN listener 100 and TSN talker 100wirelessly to a TSN network, e.g., using a 5G network as defined by3GPP. The 5G standard defined by 3GPP addresses factory use casesthrough a plurality of features, especially on the RAN (e.g., providing5G NR) to make it more reliable and reduce the transmit latency comparedto an evolved UMTS radio access network (E-UTRAN, i.e., the radio accesstechnology of 4G LTE).

The 5G network comprises the UE 100, the RAN 730 instantiated as the gNB200 and nodes 300-4 within the core network (5G CN). An example for the5G network architecture is illustrated on the left-hand side in FIG. 10.An example for the TSN network architecture is illustrated on theright-hand side in FIG. 10.

Both technologies, the 5G network and the TSN network, define ownmethods for network management and/or configuration. Differentmechanisms to achieve communication determinism are arranged to enableend-to-end deterministic networking to support TSN streams, e.g., forindustrial networks. A study item for upcoming 3GPP release 16 has beeninitiated in the 3GPP document RP-181479 to support TSN, e.g., forfactory automation use cases.

Herein, the UE 100 being the radio device connected to the RAN 710 (andthus to the 5G network) may also be referred to as a 5G endpoint. Adevice connected to the TSN network (also, TSN domain) may be referredto as a TSN endpoint.

Despite what is shown in FIG. 10, it is also possible that the UE 100 isnot connected to a single endpoint but instead to a TSN networkcomprising at least one TSN bridge and at least one endpoint. The UE 100is then part of a TSN-5G gateway.

The control plane of the 5G network may comprise at least one of aNetwork Repository Function (NRF), the AMF 300-4, a Session ManagementFunction (SMF), a Network Exposure Function (NEF), a Policy ControlFunction (PCF), and a Unified Data Management (UDM).

A data plane of the 5G network comprises a User Plane Function (UPF), atleast one embodiment of the RBS 200, and/or at least one embodiment ofthe UE 100.

A TSN listener 1002 may be embodied by or performed (e.g., as anapplication) at the UE 100. While the UE 100 operates as or is used bythe TSN listener 1002 in the fourth example of the communication system700 shown in FIG. 10, the UE 100 may alternatively or additionallyoperate as a TSN talker in any example. Optionally, a TSN talker 1004 isembodied by another UE 100 connected through the same or another RBS 200to the communication system 700.

The step 604 of the method 600 may be implemented according to at leastone of the following variants (e.g., in the context of any of the fourexamples of the communication system 700 in FIGS. 7 to 10). In a firstvariant, the CNC 300-2 configures the gNB 200 by sending theconfiguration message 722-2. In a second variant, the CUC 300-3 sendsthe configuration message 722-3 to the AMF 300-4 and, thereby,configures the gNB 200. For example, the AMF 300-4 forwards theconfiguration message 722-3 to the gNB 200 or derives the configurationmessage 722-4 from the configuration message 722-3. In a third variant(not shown), the CUC 300-3 sends the configuration message 722-3 to thegNB 200. In a fourth variant (not shown), the CNC 300-2 sends theconfiguration message 722-2 to the AMF 300-4. Optionally, e.g., in anyof the variants, the AMF 300-4 implements at least one of the CNC 300-2and the CUC 300-3.

Alternatively or in addition, the CNC 300-2 sends the configurationmessage 722-2 to the network component 300-1 (e.g., a switch or arouter) and, thereby, configures the gNB 200. For example, the networkcomponent 300-1 forwards the configuration message 722-2 to the gNB 200or derives the configuration message 722-1 from the configurationmessage 722-2.

While the technique is described herein with embodiments in the contextmanufacturing and factory automation for clarity and concreteness, thetechnique may further be applicable to automotive communication and homeautomation.

FIG. 11 shows a signaling diagram 1100 for TSN Stream Configurationinvolving exemplary embodiments of the device 100 (e.g., a UE 100 as theTSN talker and/or a UE 100 as the TSN listener) and exemplaryembodiments of the device 300 (namely 300-1, 300-2 and 300-3). Whilethese multiple embodiments of the devices 100 and 300 are shown anddescribed in combination, any subcombination may be realized. Forexample, only one of the network component 300-1, the CNC 300-2 and theCUC 300-3 may embody the device 300. Alternatively or in addition, onlyone of the TSN talker and the TSN listener may be an embodiment of thedevice 100.

The steps for the TSN Stream Configuration (e.g., according to thesignaling diagram 1100) may be performed after the UE 100 has decided toaccess (e.g., radio-connect and/or attach to) the RBS 200 (not shown inFIG. 10 for simplicity) based on the SI received in the step 402. Thestep 404 may initiate at least one of the steps for the TSN StreamConfiguration.

Each UE 100 implementing a TSN talker or a TSN listener isradio-connected through an embodiment of the RBS 200 to at least one ofthe network component 300-1, the CNC 300-2 and the CUC 300-3. The UEs100 may be radio-connected through the same RBS 200 or different RBSs200. The TSN Stream Configuration may be compatible or consistent withIEEE 802.1Qcc.

The TSN Stream Configuration (i.e., setting up the at least one TSNstream in the TSN network) according to the fully centralizedconfiguration scheme comprises at least one of the following steps.

In a first step 1102, the CUC 300-3 may take input from e.g. anindustrial application or engineering tool (e.g. a programmable logiccontroller, PLC), which specifies for example the devices, which aresupposed to exchange time-sensitive streams (i.e., TSN streams). The PLCmay be adapted to control manufacturing processes, such as assemblylines, or robotic devices, or any activity that requires highreliability control and/or ease of programming and process faultdiagnosis.

In a second step 1104, the CUC 300-2 reads the capabilities of endstations and applications in the TSN network, which includes periodand/or interval of user traffic and payload sizes.

In a third step 1106, based on this above information, the CUC 300-3creates at least one of a StreamID as an identifier for each TSN stream,a StreamRank, and UsertoNetwork Requirements.

In a fourth step 1108, the CNC 300-2 discovers the physical networktopology using, for example, a Link Layer Discovery Protocol (LLDP) andany network management protocol.

In a fifth step 1110, the CNC 300-2 uses a network management protocolto read TSN capabilities of bridges (e.g., IEEE 802.1Q, 802.1AS,802.1CB) in the TSN network.

In a sixth step 1112, the CUC 300-3 initiates join requests to configurethe at least one TSN stream in order to configure network resources atthe bridges 300-1 for a TSN stream from one TSN talker 100 to one TSNlistener 100.

In a seventh step, a group of the TSN talker 100 and the TSN listener100 (i.e., a group of elements specifying a TSN stream) is created bythe CUC 300-3, e.g., as specified in the standard IEEE 802.1Qcc, clause46.2.2.

In an eighth step 1114, the CNC 300-2 configures the TSN domain, checksphysical topology and checks if the time sensitive streams are supportedby bridges in the network, and performs path and schedule computation ofstreams.

In a ninth step 1116, the CNC 300-2 configures TSN features in bridgesalong the path in the TSN network.

In a tenth step 1118, the CNC 300-2 returns status (e.g., success orfailure) for resulting resource assignment for the at least one TSNstream to the CUC 300-3.

In a eleventh step 1120, the CUC 300-3 further configures end stations(wherein a protocol used for this information exchange may be out of thescope of the IEEE 802.1Qcc specification) to start the user planetraffic exchange, as defined initially between the TSN listener 100 andthe TSN talker 100.

In the TSN network, the streamID is used to uniquely identify streamconfigurations. It is used to assign TSN resources to the TSN stream ofa TSN talker. The streamID comprises the two tuples MacAddress andUniqueID. The MacAddress is associated with the TSN talker 100. TheUniqueID distinguishes between multiple streams within end stationsidentified by the same MacAddress.

Any embodiment and implementation of the technique may encode the SI 712in dedicated information elements in one or more SIBs. According to thestep 402 and 502, a UE 100 is enabled to detect TSN features that aresupported by the RBS 200 of the network and/or how they are supported.The UE 100 receives the SI 712 before it attaches to the network, andcan check first by listening to an SIB message comprising the SI 712.The received SI 712 may be forward to the TSN application 1002 or 1004the UE 100 is serving, and/or the UE 100 uses the SI 712 to setup aconnection to the 5G network.

Any embodiment of the RBS 200 may implement the technique by includingone or more SIBs and/or information elements in SIBs for indicating tothe UE 100 the TSN features and/or TSN configuration details supportedby the 5G network, e.g., specifically be the RBS 200.

Any embodiment of the UE 100 may implement the step 402 by reading theone or more SIBs and/or the information element included therein.Optionally, the included information as to supported TSN features and/orTSN configuration are forwarded to the TSN applications it is serving.Conditionally, i.e., depending on the features indicated as supported inthe SI 712, the information is used to establish a connection to the RBS(e.g., to the 5G network).

An (e.g., expandable) example of a SIB block structure for the SI 712 inthe steps 402 and 502 is outlined below using Abstract Syntax NotationOne (ASN.1). The same information may also be included in theconfiguration message 722 of the method 600.

-   -   ASN1START        SystemInformationBlockType16-r11::=SEQUENCE {    -   TSNFeatures SEQUENCE {        -   Time synchronisation Boolean        -   Time Synchronisation accuracy Integer; OPTIONAL, —Need OR        -   FRER Boolean        -   TSN configuration details Integer        -   Credit based shaper boolean        -   Time aware shaper boolean        -   Max. Latency added by 5G network integer}            }

Furthermore, the SIB blocks may be adapted to future versions of TSNfeatures by, for example, introducing reserved fields to be defined inthe future.

For end-to-end time synchronization (e.g., provisioning of an absolutetime reference) multiple ways of implementation are possible. The SI 712may comprise information about how the time synchronization is treatedby the RAN (e.g., the 5G network).

The “FRER” parameter refers to the redundancy features that aresupported by the 5G network. In case the network does not supportredundancy, there is no need to establish, e.g., redundant protocol dataunit (PDU) sessions.

The TSN configuration may include the presence of the CUC 300-3 and/orthe CNC 300-2 in the TSN network and/or specific TSN configurationschemes that are supported.

The “Max. Latency added by 5G network” parameter may be used to signal aQoS level in terms of latency and/or reliability that can be supportedby the 5G network to the UE 100. A field representing this parameter maycomprise a latency value (e.g., in milliseconds) that can be guaranteedwith a sufficient reliability or a classification value (e.g.,non-real-time, real-time, hard-real-time or similar). The value may beindicated by a predefined index value. This information may be used bythe UE 100 (or the endpoint 1002 or 1004 of the TSN network behind theUE 100) to find out before connection establishment if a connection tothe RBS 200 (or the 5G network) will be able to support the requirementsof the TSN application 1002 or 1004, or not.

The RBS 200 (e.g., a gNB) may further include a current cell load and/orother metrics into the calculation of that field. Optionally, the SI 712is indicative of a traffic shaper support, which refers to a quality ofservice (QoS) that may be guaranteed by the RBS (e.g., the 5G network).For example, the SI 712 may be indicative of whether the shaper is basedon credit (e.g., data volume per time and UE) or a time aware shaper(TAS) for TSN.

FIG. 12 shows a signaling diagram 1200 resulting from implementations ofthe methods 400, 500 and 600 being performed by embodiments of thedevices 100, 200 and 300, respectively. More specifically, the techniqueenables an embodiment of the UE 100 to become aware of TSN featuressupported by the network over the SI 712 included in one or more SIBs.While the signaling diagram 1200 (and the corresponding flowchart) forTSN stream configuration uses the fully centralized configuration scheme(e.g., as shown in FIG. 9), the technique is readily applicable to otherconfiguration schemes (e.g., as shown in FIG. 7 or 8).

The implementations of the methods 400, 500 and 600 enable the UE 100 toget aware of TSN features supported by the network and/or specificallyby the RBS 200 over the one or more SIBs including the SI 712.

In the step 604, a 5G core function (e.g., the AMF 300-4) indicates bysending the configuration message 722 to specific RBSs 200 (e.g., gNBs)which TSN features (e.g., according to above non-exhaustive list) aresupported or supposed to be enabled (e.g., only a subset of all gNBsmight support TSN) and how these TSN features are supported.

Responsive to the reception of the configuration message 722 (e.g., anyof the above implementations 722-1 to 722-4), the RBS 200 (e.g., a gNB)generates the SI 712 (e.g., the SIB block information as outlined above)and starts broadcasting the SI 712, e.g. over the DL-SCH, in the step502.

The UE 100 receives and/or reads the SI 712 in the SIB in the step 402.Optionally, the UE 100 transfers at least some of the information in theSI 712 to the TSN application 1002 or 1004, e.g., a list of the TSNfeatures supported by the RBS 200. The TSN application 1002 or 1004 mayrequest a TSN connection towards the UE 100, if the supported list ofTSN features is sufficient, as an example for the conditionality orselectivity in the step 404.

For initiating the TSN stream in the step 404, the UE 100 goes into RRCconnected mode if not already in that mode and requests a PDU session,which may be of Ethernet type. UE may further provide information bymeans of NAS signaling on which TSN features are required.

A TSN controller (e.g., the CNC 300-2) receives a confirmation from theCN 730 and performs path computation and time scheduling. TSN streamcommunication starts, wherein the RBS 200 supports the TSN streamaccording to the step 504.

In any embodiment, the UE 100 may defer or refrain from requesting theRRC connection setup in the step 404, if the TSN application requirescertain TSN features and the UE 100 did not receive in the SIB broadcast402 that one or more of these features are supported, as an example forthe conditionality or selectivity in the step 404.

In same or another embodiment, the UE 100 reads the SI 712 (i.e., theTSN information included in the one or more SIBs) of multiple RBSs 200(e.g., gNBs) and selects the RBS 200, which best fulfills the TSNrequirements of the UE 100. If all RBS 200 fulfill the requirements, theUE 100 may act according to a selection rule, e.g. selecting the RBS 200indicating the lowest latency.

In any embodiment, the UE 100 may store the SI 712 received in the step402. The technique may be implemented as described up until andincluding the step 402. When the TSN application 1002 or 1004 requests aTSN communication (i.e., one or more TSN streams), the UE 100 uses thestored SI 712 to either setup the at least one TSN stream in thesupported way or declines the TSN request if it is not supported. The UE100 may further use the SI 712 from the SIB, e.g., to initialize packetfiltering of packets coming in for TSN transmission. Furthermore, thereceived SI 712 may be used to establish a default PDU session with the5G network.

FIG. 13 shows a schematic block diagram for an embodiment of the device100. The device 100 comprises one or more processors 1304 for performingthe method 400 and memory 1306 coupled to the processors 1304. Forexample, the memory 1306 may be encoded with instructions that implementat least one of the modules 102 and 104.

The one or more processors 1304 may be a combination of one or more of amicroprocessor, controller, microcontroller, central processing unit,digital signal processor, application specific integrated circuit, fieldprogrammable gate array, or any other suitable computing device,resource, or combination of hardware, microcode and/or encoded logicoperable to provide, either alone or in conjunction with othercomponents of the device 100, such as the memory 1306, data transmitterfunctionality, TSN talker functionality, data receiver functionality,and/or TSN listener functionality. For example, the one or moreprocessors 1304 may execute instructions stored in the memory 1306. Suchfunctionality may include providing various features and steps discussedherein, including any of the benefits disclosed herein. The expression“the device being operative to perform an action” may denote the device100 being configured to perform the action.

As schematically illustrated in FIG. 13, the device 100 may be embodiedby a UE 1300, e.g., radio-connected or radio-connectable to the RAN 710.The UE 1300 comprises a radio interface 1302 coupled to the device 100for radio communication with one or more RBSs.

FIG. 14 shows a schematic block diagram for an embodiment of the device200. The device 200 comprises one or more processors 1404 for performingthe method 500 and memory 1406 coupled to the processors 1404. Forexample, the memory 1406 may be encoded with instructions that implementat least one of the modules 202 and 204.

The one or more processors 1404 may be a combination of one or more of amicroprocessor, controller, microcontroller, central processing unit,digital signal processor, application specific integrated circuit, fieldprogrammable gate array, or any other suitable computing device,resource, or combination of hardware, microcode and/or encoded logicoperable to provide, either alone or in conjunction with othercomponents of the device 100, such as the memory 1406, data receiver orRAN functionality. For example, the one or more processors 1404 mayexecute instructions stored in the memory 1406. Such functionality mayinclude providing various features and steps discussed herein, includingany of the benefits disclosed herein. The expression “the device beingoperative to perform an action” may denote the device 200 beingconfigured to perform the action.

As schematically illustrated in FIG. 14, the device 200 may be embodiedby a RBS 1400, e.g., of the RAN 710. The RBS 1400 comprises a radiointerface 1402 coupled to the device 200 for radio communication withone or more UEs.

FIG. 15 shows a schematic block diagram for an embodiment of the device300. The device 300 comprises one or more processors 1504 for performingthe method 600 and memory 1506 coupled to the processors 1504. Forexample, the memory 1506 may be encoded with instructions that implementat least one of the modules 302 and 304.

The one or more processors 1504 may be a combination of one or more of amicroprocessor, controller, microcontroller, central processing unit,digital signal processor, application specific integrated circuit, fieldprogrammable gate array, or any other suitable computing device,resource, or combination of hardware, microcode and/or encoded logicoperable to provide, either alone or in conjunction with othercomponents of the device 200, such as the memory 1506, base stationfunctionality or RAN functionality. For example, the one or moreprocessors 1504 may execute instructions stored in the memory 1506. Suchfunctionality may include providing various features and steps discussedherein, including any of the benefits disclosed herein. The expression“the device being operative to perform an action” may denote the device300 being configured to perform the action.

As schematically illustrated in FIG. 15, the device 300 may be embodiedby an AMF 1500, e.g., of the CN 730. The AMF 1500 comprises an interface1502 (e.g., an S1 interface or NG2 reference point) coupled to thedevice 300 for radio communication with one or more UEs.

With reference to FIG. 16, in accordance with an embodiment, acommunication system 1600 includes a telecommunication network 1610,such as a 3GPP-type cellular network, which comprises an access network1611, such as the RAN, and an embodiment of the CN 1614. The accessnetwork 1611 comprises a plurality of RBSs 1612 a, 1612 b, 1612 c, suchas NBs, eNBs, gNBs or other types of wireless access points, eachdefining a corresponding coverage area 1613 a, 1613 b, 1613 c. Each RBS1612 a, 1612 b, 1612 c is connectable to the core network 1614 over awired or wireless connection 1615. A first UE 1691 located in coveragearea 1613 c is configured to wirelessly connect to, or be paged by, thecorresponding RBS 1612 c. A second UE 1692 in coverage area 1613 a iswirelessly connectable to the corresponding RBS 1612 a. While aplurality of UEs 1691, 1692 are illustrated in this example, thedisclosed embodiments are equally applicable to a situation where a soleUE is in the coverage area or where a sole UE is connecting to thecorresponding RBS 1612.

The telecommunication network 1610 is itself connected to a hostcomputer 1630, which may be embodied in the hardware and/or software ofa standalone server, a cloud-implemented server, a distributed server oras processing resources in a server farm. The host computer 1630 may beunder the ownership or control of a service provider, or may be operatedby the service provider or on behalf of the service provider. Theconnections 1621, 1622 between the telecommunication network 1610 andthe host computer 1630 may extend directly from the core network 1614 tothe host computer 1630 or may go via an optional intermediate network1620. The intermediate network 1620 may be one of, or a combination ofmore than one of, a public, private or hosted network; the intermediatenetwork 1620, if any, may be a backbone network or the Internet; inparticular, the intermediate network 1620 may comprise two or moresub-networks (not shown).

The communication system 1600 of FIG. 16 as a whole enables connectivitybetween one of the connected UEs 1691, 1692 and the host computer 1630.The connectivity may be described as an over-the-top (OTT) connection1650. The host computer 1630 and the connected UEs 1691, 1692 areconfigured to communicate data and/or signaling via the OTT connection1650, using the access network 1611, the core network 1614, anyintermediate network 1620 and possible further infrastructure (notshown) as intermediaries. The OTT connection 1650 may be transparent inthe sense that the participating communication devices through which theOTT connection 1650 passes are unaware of routing of uplink and downlinkcommunications. For example, a RBS 1612 may not or need not be informedabout the past routing of an incoming downlink communication with dataoriginating from a host computer 1630 to be forwarded (e.g., handedover) to a connected UE 1691. Similarly, the RBS 1612 need not be awareof the future routing of an outgoing uplink communication originatingfrom the UE 1691 towards the host computer 1630.

Example implementations, in accordance with an embodiment, of the UE,the RBS and host computer discussed in the preceding paragraphs will nowbe described with reference to FIG. 17. In a communication system 1700,a host computer 1710 comprises hardware 1715 including a communicationinterface 1716 configured to set up and maintain a wired or wirelessconnection with an interface of a different communication device of thecommunication system 1700. The host computer 1710 further comprisesprocessing circuitry 1718, which may have storage and/or processingcapabilities. In particular, the processing circuitry 1718 may compriseone or more programmable processors, application-specific integratedcircuits, field programmable gate arrays or combinations of these (notshown) adapted to execute instructions. The host computer 1710 furthercomprises software 1711, which is stored in or accessible by the hostcomputer 1710 and executable by the processing circuitry 1718. Thesoftware 1711 includes a host application 1712. The host application1712 may be operable to provide a service to a remote user, such as a UE1730 connecting via an OTT connection 1750 terminating at the UE 1730and the host computer 1710. In providing the service to the remote user,the host application 1712 may provide user data, which is transmittedusing the OTT connection 1750.

The communication system 1700 further includes a RBS 1720 provided in atelecommunication system and comprising hardware 1725 enabling it tocommunicate with the host computer 1710 and with the UE 1730. Thehardware 1725 may include a communication interface 1726 for setting upand maintaining a wired or wireless connection with an interface of adifferent communication device of the communication system 1700, as wellas a radio interface 1727 for setting up and maintaining at least awireless connection 1770 with a UE 1730 located in a coverage area (notshown in FIG. 17) served by the RBS 1720. The communication interface1726 may be configured to facilitate a connection 1760 to the hostcomputer 1710. The connection 1760 may be direct or it may pass througha core network (not shown in FIG. 17) of the telecommunication systemand/or through one or more intermediate networks outside thetelecommunication system. In the embodiment shown, the hardware 1725 ofthe RBS 1720 further includes processing circuitry 1728, which maycomprise one or more programmable processors, application-specificintegrated circuits, field programmable gate arrays or combinations ofthese (not shown) adapted to execute instructions. The RBS 1720 furtherhas software 1721 stored internally or accessible via an externalconnection.

The communication system 1700 further includes the UE 1730 alreadyreferred to. Its hardware 1735 may include a radio interface 1737configured to set up and maintain a wireless connection 1770 with a RBSserving a coverage area in which the UE 1730 is currently located. Thehardware 1735 of the UE 1730 further includes processing circuitry 1738,which may comprise one or more programmable processors,application-specific integrated circuits, field programmable gate arraysor combinations of these (not shown) adapted to execute instructions.The UE 1730 further comprises software 1731, which is stored in oraccessible by the UE 1730 and executable by the processing circuitry1738. The software 1731 includes a client application 1732. The clientapplication 1732 may be operable to provide a service to a human ornon-human user via the UE 1730, with the support of the host computer1710. In the host computer 1710, an executing host application 1712 maycommunicate with the executing client application 1732 via the OTTconnection 1750 terminating at the UE 1730 and the host computer 1710.In providing the service to the user, the client application 1732 mayreceive request data from the host application 1712 and provide userdata in response to the request data. The OTT connection 1750 maytransfer both the request data and the user data. The client application1732 may interact with the user to generate the user data that itprovides.

It is noted that the host computer 1710, RBS 1720 and UE 1730illustrated in FIG. 17 may be identical to the host computer 1630, oneof the RBSs 1612 a, 1612 b, 1612 c and one of the UEs 1691, 1692 of FIG.16, respectively. This is to say, the inner workings of these entitiesmay be as shown in FIG. 17 and independently, the surrounding networktopology may be that of FIG. 16.

In FIG. 17, the OTT connection 1750 has been drawn abstractly toillustrate the communication between the host computer 1710 and the useequipment 1730 via the RBS 1720, without explicit reference to anyintermediary devices and the precise routing of messages via thesedevices. Network infrastructure may determine the routing, which it maybe configured to hide from the UE 1730 or from the service provideroperating the host computer 1710, or both. While the OTT connection 1750is active, the network infrastructure may further take decisions bywhich it dynamically changes the routing (e.g., on the basis of loadbalancing consideration or reconfiguration of the network).

The wireless connection 1770 between the UE 1730 and the RBS 1720 is inaccordance with the teachings of the embodiments described throughoutthis disclosure. One or more of the various embodiments improve theperformance of OTT services provided to the UE 1730 using the OTTconnection 1750, in which the wireless connection 1770 forms the lastsegment. More precisely, the teachings of these embodiments may reducethe latency and improve the data rate and thereby provide benefits suchas better responsiveness.

A measurement procedure may be provided for the purpose of monitoringdata rate, latency and other factors on which the one or moreembodiments improve. There may further be an optional networkfunctionality for reconfiguring the OTT connection 1750 between the hostcomputer 1710 and UE 1730, in response to variations in the measurementresults. The measurement procedure and/or the network functionality forreconfiguring the OTT connection 1750 may be implemented in the software1711 of the host computer 1710 or in the software 1731 of the UE 1730,or both. In embodiments, sensors (not shown) may be deployed in or inassociation with communication devices through which the OTT connection1750 passes; the sensors may participate in the measurement procedure bysupplying values of the monitored quantities exemplified above, orsupplying values of other physical quantities from which software 1711,1731 may compute or estimate the monitored quantities. The reconfiguringof the OTT connection 1750 may include message format, retransmissionsettings, preferred routing etc.; the reconfiguring need not affect theRBS 1720, and it may be unknown or imperceptible to the RBS 1720. Suchprocedures and functionalities may be known and practiced in the art. Incertain embodiments, measurements may involve proprietary UE signalingfacilitating the host computer's 1710 measurements of throughput,propagation times, latency and the like. The measurements may beimplemented in that the software 1711, 1731 causes messages to betransmitted, in particular empty or “dummy” messages, using the OTTconnection 1750 while it monitors propagation times, errors etc.

FIG. 18 is a flowchart illustrating a method implemented in acommunication system, in accordance with one embodiment. Thecommunication system includes a host computer, a RBS and a, UE which maybe those described with reference to FIGS. 16 and/or 17. For simplicityof the present disclosure, only drawing references to FIG. 18 will beincluded in this section. In a first step 1810 of the method, the hostcomputer provides user data. In an optional substep 1811 of the firststep 1810, the host computer provides the user data by executing a hostapplication. In a second step 1820, the host computer initiates atransmission carrying the user data to the UE. In an optional third step1830, the RBS transmits to the UE the user data which was carried in thetransmission that the host computer initiated, in accordance with theteachings of the embodiments described throughout this disclosure. In anoptional fourth step 1840, the UE executes a client applicationassociated with the host application executed by the host computer.

FIG. 19 is a flowchart illustrating a method implemented in acommunication system, in accordance with one embodiment. Thecommunication system includes a host computer, a RBS and a UE, which maybe those described with reference to any one of the FIGS. 1 to 17. Forsimplicity of the present disclosure, only drawing references to FIG. 19will be included in this section. In a first step 1910 of the method,the host computer provides user data. In an optional substep (not shown)the host computer provides the user data by executing a hostapplication. In a second step 1920, the host computer initiates atransmission carrying the user data to the UE. The transmission may passvia the RBS, in accordance with the teachings of the embodimentsdescribed throughout this disclosure. In an optional third step 1930,the UE receives the user data carried in the transmission.

As has become apparent from above description, embodiments of thetechnique enable a UE to detect whether TSN and/or which or howparticular TSN features are supported by wireless access (e.g., in a 5Gnetwork) in order to be able to set up a TSN connection for the TSNapplication requiring these features.

Same or further embodiments can reduce time and/or avoid a lot ofsignaling complexity (e.g., as compared to the time and signalingcomplexity that would be part of a conventional radio access, whereinthe UE establishes first a connection to the network). The embodimentscan broadcasting and receive this information right away before the UEis radio-connected to the RAN.

Many advantages of the present invention will be fully understood fromthe foregoing description, and it will be apparent that various changesmay be made in the form, construction and arrangement of the units anddevices without departing from the scope of the invention and/or withoutsacrificing all of its advantages. Since the invention can be varied inmany ways, it will be recognized that the invention should be limitedonly by the scope of the following claims.

The invention claimed is:
 1. A method of handling Time-SensitiveNetworking, TSN, over a radio access network, RAN, the methodcomprising: receiving system information from a radio base station ofthe RAN, wherein the system information is implicative or indicative ofsupport for TSN through the radio base station; and establishing orinitiating to establish, depending on the received system information,at least one TSN stream of the TSN through the radio base station. 2.The method of claim 1, wherein the step of establishing or initiating toestablish, depending on the received system information, the at leastone TSN stream comprises selectively establishing or selectivelyinitiating to establish the at least one TSN stream, wherein theselectivity is dependent on the received system information.
 3. Themethod of claim 1, wherein the step of establishing or initiating toestablish the at least one TSN stream comprises selectively performingor selectively initiating to perform at least one of: a random accessprocedure with the radio base station of the RAN; a radio resourcecontrol, RRC, connection setup with the radio base station of the RAN;and a network attach procedure with a core network connected to the RAN,wherein the selectivity is dependent on the received system information.4. The method of claim 1, wherein the establishing step comprises:performing or initiating to perform a TSN application that uses the atleast one established TSN stream.
 5. The method of claim 4, wherein theselectivity is fulfilled if the received system information isindicative of TSN features required by the TSN application.
 6. Themethod of claim 4, wherein the step of receiving the system informationis performed with respect to each of a plurality of radio base stationsof the RAN, and wherein the step of establishing or initiating toestablish the at least one TSN stream comprises selecting, among theplurality of radio base stations, the radio base station the systeminformation of which is indicative of TSN features required by the TSNapplication.
 7. The method of claim 4, further comprising the step of:sending a control message to the core network, the control message beingindicative of TSN features required by the TSN application.
 8. Themethod of claim 1, wherein the system information is implicative orindicative of at least one TSN feature supported by or through the radiobase station.
 9. The method of claim 8, wherein the at least one TSNfeature comprises at least one of: a time-synchronization of componentsprocessing the at least one TSN stream of the TSN over the RAN; alatency bound for the at least one TSN stream of the TSN over the RAN;and a reliability measure for the at least one TSN stream of the TSNover the RAN.
 10. The method of claim 9, wherein the system informationis indicative of a TSN configuration for the TSN through the radio basestation.
 11. The method of claim 10, wherein the TSN configuration isindicative of an availability of at least one of a Central NetworkingConfiguration, CNC, and a Central User Configuration, CUC.
 12. Themethod of claim 1, wherein the system information is broadcasted fromthe radio base station.
 13. The method of claim 1, wherein the systeminformation is comprised in one or more system information blocks, SIBs.14. A method of announcing Time-Sensitive Networking, TSN, over a radioaccess network, RAN, the method comprising: transmitting systeminformation from a radio base station of the RAN, wherein the systeminformation is implicative or indicative of support for TSN through theradio base station; and supporting, according to the transmitted systeminformation, at least one TSN stream of the TSN through the radio basestation.
 15. The method of claim 14, further comprising: receiving aconfiguration message indicative of the support for TSN from a corenetwork, CN, at the radio base station, wherein the transmitted systeminformation is derived from the received configuration message.
 16. Themethod of claim 15, wherein the system information is implicative orindicative of at least one TSN feature supported by or through the radiobase station.
 17. The method of claim 14, wherein the system informationis broadcasted in one or more system information blocks, SIBs.
 18. Themethod of claim 14, wherein the system information is indicative of aTSN configuration for the TSN through the radio base station.
 19. Adevice for handling Time-Sensitive Networking, TSN, over a radio accessnetwork, RAN, the device comprising at least one processor and a memory,said memory comprising instructions executable by said at least oneprocessor, whereby the device is operative to: receive systeminformation from a radio base station of the RAN, wherein the systeminformation is implicative or indicative of support for TSN through theradio base station; and establish or initiate establishing, depending onthe received system information, at least one TSN stream of the TSNthrough the radio base station.
 20. The device of claim 19, furtheroperative to selectively establish or selectively initiate to establishthe at least one TSN stream based on the received system information.21. A device for announcing Time-Sensitive Networking, TSN, over a radioaccess network, RAN, the device comprising at least one processor and amemory, said memory comprising instructions executable by said at leastone processor, whereby the device is operative to: transmit systeminformation from a radio base station of the RAN, wherein the systeminformation is implicative or indicative of support for TSN through theradio base station; and support, according to the transmitted systeminformation, at least one TSN stream of the TSN through the radio basestation.
 22. The device of claim 21, further operative to receive aconfiguration message indicative of the support for TSN from a corenetwork, CN, at the radio base station, wherein the transmitted systeminformation is derived from the received configuration message.